chore: rename goat-code binary from goat to goat-code#111
Merged
Conversation
jbj338033
force-pushed
the
chore/rename-goat-code-binary
branch
from
3896c17 to
de7a885
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The goat-code binary was named
goat, colliding with thegoatagent CLI (separate repo) which installs a binary of the same name. This renames the goat-code release binary togoat-codeacross the[[bin]], self-update paths, release workflow, install script, and user-facing command hints. The goat agent's bridge already expects agoat-codeexecutable, so this aligns them.Verification
cargo fmt --all --check— passedcargo clippy -p goat-code -p goat-update --all-targets -- -D warnings— passedcargo test -p goat-code -p goat-update— passed